Skip to content

Add Access Denied mitigation steps due to GPO settings#273

Open
donha-ms wants to merge 1 commit intoAzure:mainfrom
donha-ms:users/donha/access-denied-gpo
Open

Add Access Denied mitigation steps due to GPO settings#273
donha-ms wants to merge 1 commit intoAzure:mainfrom
donha-ms:users/donha/access-denied-gpo

Conversation

@donha-ms
Copy link
Copy Markdown
Contributor

No description provided.

Copy link
Copy Markdown

@mchen-msft mchen-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new troubleshooting section to the Azure Local LCM “access denied” TSG to help validate and mitigate remote logon failures caused by domain GPO user-rights assignments.

Changes:

  • Adds a new “Access Denied because remote logon related GPO policy is applied” section with symptoms, validation script, and mitigation steps.
  • Introduces a PowerShell validation script to detect when local admins are blocked by SeDenyNetworkLogonRight and attempts to identify the applying GPO.
  • Documents the GPO location and provides a mitigation workflow (update GPO + gpupdate /force).

Comment thread TSG/LCM/access-denied-lcm-user.md Outdated
Comment thread TSG/LCM/access-denied-lcm-user.md Outdated
Comment thread TSG/LCM/access-denied-lcm-user.md
Comment thread TSG/LCM/access-denied-lcm-user.md Outdated
@donha-ms donha-ms force-pushed the users/donha/access-denied-gpo branch from 45ba739 to 514aac3 Compare April 16, 2026 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants